src/reducers/sponsors/sponsor-customized-form-items-list-reducer.js (1)

128-138: ⚠️ Potential issue | 🟡 Minor

Inconsistent fallback meta_fields structure.

The fallback meta_fields object when item.meta_fields.length === 0 doesn't include minimum_quantity and maximum_quantity, unlike the DEFAULT_ITEM_ENTITY definition. This could cause inconsistent state shapes.

Proposed fix

             : [
                 {
                   name: "",
                   type: "Text",
                   is_required: false,
+                  minimum_quantity: 0,
+                  maximum_quantity: 0,
                   values: []
                 }
               ]

src/reducers/sponsors/sponsor-form-items-list-reducer.js (1)

115-125: ⚠️ Potential issue | 🟡 Minor

Inconsistent fallback meta_fields structure.

Same issue as in sponsor-customized-form-items-list-reducer.js — the fallback meta_fields when item.meta_fields.length === 0 is missing minimum_quantity and maximum_quantity.

Proposed fix

             : [
                 {
                   name: "",
                   type: "Text",
                   is_required: false,
+                  minimum_quantity: 0,
+                  maximum_quantity: 0,
                   values: []
                 }
               ]

src/reducers/sponsors/sponsor-forms-list-reducer.js (1)

136-146: ⚠️ Potential issue | 🟡 Minor

Inconsistent fallback meta_fields structure.

Same pattern as other reducers — the fallback meta_fields when form.meta_fields.length === 0 is missing minimum_quantity and maximum_quantity. Consider adding them for consistent state shape.

Proposed fix

             : [
                 {
                   name: "",
                   type: "Text",
                   is_required: false,
+                  minimum_quantity: 0,
+                  maximum_quantity: 0,
                   values: []
                 }
               ]

src/reducers/sponsors_inventory/inventory-item-reducer.js (1)

29-50: ⚠️ Potential issue | 🟠 Major

Avoid shared default meta_fields object across resets.

DEFAULT_ENTITY now contains a nested object/array, but reducer paths use shallow copies, so later mutations (e.g., updating metaField.values) can leak into the default and affect new forms. Use a factory function to create fresh defaults each time.

✅ Proposed fix

-export const DEFAULT_ENTITY = {
+const createDefaultMetaField = () => ({
+  name: "",
+  type: "Text",
+  is_required: false,
+  minimum_quantity: 0,
+  maximum_quantity: 0,
+  values: []
+});
+
+export const createDefaultEntity = () => ({
   id: 0,
   code: "",
   name: "",
   description: "",
   default_quantity: 0,
   quantity_limit_per_show: 0,
   quantity_limit_per_sponsor: 0,
   early_bird_rate: 0,
   standard_rate: 0,
   onsite_rate: 0,
   images: [],
-  meta_fields: [
-    {
-      name: "",
-      type: "Text",
-      is_required: false,
-      minimum_quantity: 0,
-      maximum_quantity: 0,
-      values: []
-    }
-  ]
-};
+  meta_fields: [createDefaultMetaField()]
+});
 
-const DEFAULT_STATE = {
-  entity: DEFAULT_ENTITY,
+const DEFAULT_STATE = {
+  entity: createDefaultEntity(),
   errors: {}
 };

Then update usages (e.g., RESET/RECEIVE/ADDED/UPDATED) to spread createDefaultEntity() instead of DEFAULT_ENTITY.